Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

Standardise EmbeddingFunction generic to Embeddable across the codebase

This pull request replaces every remaining use of EmbeddingFunction[Documents] with the broader EmbeddingFunction[Embeddable]. The change eliminates lingering mypy-strict errors, unifies Python, JS and Rust expectations, and ensures that any string-like payload accepted by the Embeddable alias (single string, list of strings, etc.) can be passed to any built-in or custom embedding implementation without type ignores. No runtime behaviour changes; only static-typing signatures are updated.

The modification touches >20 embedding modules and the public client/collection APIs that accept an EmbeddingFunction. Down-stream users who explicitly parameterised their own classes or type aliases with Documents will need to migrate to Embeddable, but existing code that merely uses the functions at runtime will continue to work unchanged.

This summary was automatically generated by @propel-code-bot